Remove more leftover —es

These were leftover at various places in the documentation.

diff --git a/gtk/gtkfilechooser.c b/gtk/gtkfilechooser.c
index 2c23ea99906c7c1b7c1a6ba7c7ef7823f609724b..969eae257aa36cf9001e6a6f86538e6fc124145e 100644 (file)
--- a/gtk/gtkfilechooser.c
+++ b/gtk/gtkfilechooser.c
@@ -716,7 +716,7 @@ gtk_file_chooser_get_filename (GtkFileChooser *chooser)
  * dialog for which you already have a file name to which
  * the user may save.  For example, when the user opens an existing file and
  * then does Save As... to save a copy or
- * a modified version.  If you don’t have a file name already — for
+ * a modified version.  If you don’t have a file name already — for
  * example, if the user just created a new file and is saving it for the first
  * time, do not call this function.  Instead, use something similar to this:
  * |[<!-- language="C" -->
@@ -1068,7 +1068,7 @@ gtk_file_chooser_get_uri (GtkFileChooser *chooser)
  * dialog for which you already have a file name to which
  * the user may save.  For example, when the user opens an existing file and then
  * does Save As... to save a copy or a
- * modified version.  If you don’t have a file name already &mdash; for example,
+ * modified version.  If you don’t have a file name already — for example,
  * if the user just created a new file and is saving it for the first time, do
  * not call this function.  Instead, use something similar to this:
  * |[<!-- language="C" -->
@@ -1434,7 +1434,7 @@ gtk_file_chooser_get_files (GtkFileChooser *chooser)
  * you should use this function if you already have a file name to which the
  * user may save; for example, when the user opens an existing file and then
  * does Save As...  If you don’t have
- * a file name already &mdash; for example, if the user just created a new
+ * a file name already — for example, if the user just created a new
  * file and is saving it for the first time, do not call this function.
  * Instead, use something similar to this:
  * |[<!-- language="C" -->

diff --git a/gtk/gtkfilechooserdialog.c b/gtk/gtkfilechooserdialog.c
index 617b1fbaf57c7b58edaf1fdf473dbcda443ca590..b1295ab85382220e5d2dfb71e111b5770328076e 100644 (file)
--- a/gtk/gtkfilechooserdialog.c
+++ b/gtk/gtkfilechooserdialog.c
@@ -184,7 +184,7 @@
  *
  * This is because #GtkFileChooserDialog must intercept responses
  * and switch to folders if appropriate, rather than letting the
- * dialog terminate — the implementation uses these known
+ * dialog terminate — the implementation uses these known
  * response codes to know which responses can be blocked if
  * appropriate.
  *

diff --git a/gtk/gtktextchild.c b/gtk/gtktextchild.c
index 96e7ffd22564f95718b3225062aa0e1d9bbf8a34..61a2bfbc4aba2dbdda7330c36ba05f08ec74d079 100644 (file)
--- a/gtk/gtktextchild.c
+++ b/gtk/gtktextchild.c
@@ -422,7 +422,7 @@ gtk_text_child_anchor_get_widgets (GtkTextChildAnchor *anchor)
  * the buffer. Keep in mind that the child anchor will be
  * unreferenced when removed from the buffer, so you need to
  * hold your own reference (with g_object_ref()) if you plan
- * to use this function — otherwise all deleted child anchors
+ * to use this function — otherwise all deleted child anchors
  * will also be finalized.
  * 
  * Returns: %TRUE if the child anchor has been deleted from its buffer

diff --git a/gtk/gtktreemodel.c b/gtk/gtktreemodel.c
index 3be83088b4fe7df77ed910523676f78211adeaf0..9d1a61d68cd6cb76712d7cfd71238b09664a80fe 100644 (file)
--- a/gtk/gtktreemodel.c
+++ b/gtk/gtktreemodel.c
@@ -1,4 +1,4 @@
-/* gtktreemodel.c
+—/* gtktreemodel.c
  * Copyright (C) 2000  Red Hat, Inc.,  Jonathan Blandford <jrb@redhat.com>
  *
  * This library is free software; you can redistribute it and/or
@@ -53,7 +53,7 @@
  *
  * In order to make life simpler for programmers who do not need to
  * write their own specialized model, two generic models are provided
- * &mdash; the #GtkTreeStore and the #GtkListStore. To use these, the
+ * — the #GtkTreeStore and the #GtkListStore. To use these, the
  * developer simply pushes data into these models as necessary. These
  * models provide the data structure as well as all appropriate tree
  * interfaces. As a result, implementing drag and drop, sorting, and